Internet Surfer 2.0/Internet Surfer 2.0 (Wayzata Technology) (1996).iso/pc/text/mac/faqs.048

Text File | 1996-02-12 | 28.6 KB | 621 lines

Frequently Asked Questions (FAQS);faqs.048





8. What are the different game record formats and how can I display them?

There are several different formats for game records.  The two most
popular formats are Smart-Go and Ishi "Standard" Format.  Definitions
for these two formats are on the archive site in prog/mgt22.sh.Z and
prog/standard.sh.Z respectively.

The Smart-Go format can be read by mgt, Pon Nuki, xgoban and the Smart
Go program.  Ishi Format can be read by Many Faces of Go, Goscribe,
Goview, Contender, Smart Go Board (version 4.0 or later), and Nemesis
(version 5 and above). Ishi publishes games regularly in Ishi format.

The Liberty format is a binary format which is not common.  Many of
the files on the archive site are presently in this format.  They can
be converted to other formats with prog/convert.tar.Z.



9. What programs can I get to display go game records?

The program mgt will display game records under Unix or MSDOS.  It
does not use graphics, however.  An X11 version of mgt is under
development, but has not been released yet.  The mgt program was
created originally by Greg Hale at the request of rec.games.go readers
who wanted an interactive program that would read a series of tutorial
files posted to the net.  The program was expanded by Adrian Mariano
to edit and save game records. The purpose of mgt is to display and
edit game records in Smart-Go format.  It can be used to display a
game board.  Pieces can be placed and removed, and games can be
scored.

The program xgoban by Antoine Dumesnil de Maricourt ([e-mail])
can display and edit Smart-Go under X11.  It can also communicate with
wally to provide a graphical interface to this program.

The program Pon Nuki for the Mac is being developed by Greg Anderson
([e-mail]).  He is willing to send individuals beta test
copies.  Pon Nuki can display either Ishi or Smart-Go format.

Many Faces of Go can display only Ishi format.

The Smart-Go program itself is available for the Mac.  Also, Goscribe
for MSDOS is available through Ishi press (address above) for $59.95.
It can display and edit Ishi format.  Goview, able to display but not
edit, is available for MSDOS for $20.  Goview is free with a
subscription to Go World on disk.

     Smart Go Board, version 4.0.2, $40
     (version for Macintosh)
          Anders Kierulf
          Smart Game Board
          P.O. Box 7751
          Menlo Park, CA  94026-7751



10. How do I play games by computer?

Since computers make poor opponents, we use them to connect us to
other humans.  There are two types of computer games:  email, and
interactive.  Email games can be handled manually, by creating a board
in an editor, or only exchanging move coordinates.  The other option
is the use the unix program 'mailgo' which is included with mgt.  It
sends Smart-Go records of your game back and forth, and invokes mgt
for moves.

There are several ways to play interactive games.  Probably the most
popular is the Internet Go Server (IGS).  You can connect to the
server and look for opponents to play, or just watch a game.  To
connect directly, type "telnet icsib18.icsi.berkeley.edu 6969" on a
unix machine.  The IP number is 128.32.201.46.  A brief, outdated
introduction to the go server is available for ftp on
unmvax.cs.unm.edu in pub/go.  The internet go server is also run on
cnam.cnam.fr, but this sites do not appear to be used much.  When you
connect to the IGS, be SURE to use the port number 6969.

The IGS interface is quite awkward, so five client programs are
available to ease your interaction with the server.  They are
prog/igc050.sh.Z, an ascii client for unix, prog/xigs_v1.0.sh.Z and
prog/xgospel.sh.Z, X11 clients for unix, prog/gs039.sit.hqx, a
Macintosh client, and prog/pcig42z.exe, an IBM PC client.  All four
programs are available on ftp.u.washington.edu.

Another interactive options is the internet go program, available on
the archive site as prog/inetgo72.sh.Z, which allows BSD Unix users to
play interactive games with ascii text screens.  The xgosh program
(prog/xgosh17.sh.Z on the archive site) allows people with X-Windows
to play interactive games with a graphical board.  The two interactive
programs are NOT compatible.

To help find suitable opponents, check out the go players email
address list, available on the archive site as go-players, and also
posted monthly with this FAQ.

There is a standard go modem protocol which is used by go programs for
modem play.  It is implemented in Many Faces of Go, Nemesis, and
Telego (a shareware go modem program for the IBM PC).  The protocol
spec and sample code are available from the archive site as
info/protocol.Z.

Fotland's program, Many Faces of Go for X Windows on HP machines
supports two players on two screens.



11. Where can I get go equipment, books, etc?

     Ishi Press International    Ishi Press International
     76 Bonaventura Drive      20 Bruges Place
     San Jose, CA  95134      London England NW1 OTE
     Tel: [phone]
     FAX: [phone]      071 284 4898

     Ishi Press
     1301-5 Yabata
     Chigasaki-Shi
     Kanagawa-ken 253
     (0467)83-4369
     (0467)83-4710 (fax)
     Japan



12. What are the dimensions of a go board?

The official size according to Nihon Ki-in is 45.45 x 42.42 (cm).
Measurements of an Ishi board indicate that the lines are 0.8 mm
thick and the hoshi points are 3 mm in diameter.

Stones are supposed to be 20-21 mm in diameter.



13. What books should I read?

A list of books is on the archive site:  info/books.Z
Xref: bloom-picayune.mit.edu comp.groupware:1588 news.answers:4611
Path: bloom-picayune.mit.edu!enterpoop.mit.edu!senator-bedfellow.mit.edu!senator-bedfellow.mit.edu!usenet
From: [e-mail] (David Stodolsky)
Newsgroups: comp.groupware,news.answers
Subject: Introduction to comp.groupware (Periodic informational Posting)
Supersedes: <[e-mail]>
Followup-To: comp.groupware
Date: 15 Dec 1992 18:59:52 GMT
Organization: Roskilde University
Lines: 321
Approved: [e-mail]
Distribution: world
Expires: 12 Jan 1993 18:59:02 GMT
Message-ID: <[e-mail]>
NNTP-Posting-Host: pit-manager.mit.edu
Summary: Guidelines for posting to the Usenet newsgroup comp.groupware.
Keywords: CSCW, orgware, group, interactive, shared, environments
X-Last-Updated: 1992/10/06

Archive-name: groupware-intro
Last-modified: 1992/10/6
Version: 1.2

Please read carefully:
Any article posted to comp.groupware uses a minimum of ten hours of
readers' time. Do not post test messages to comp.groupware (see section
5 below).

This article is posted automatically every 14 days to introduce the
group to the more than one thousand new readers that have subscribed
during that period.

---------------- Contents (and revision information) ------------

Sections in this article (Revised in last modification)

0. Groupware is software and hardware for shared interactive
environments. (Revised ordering of paragraphs)
1. Set your distribution to "world".
2. Sign your article.
3. Comp.groupware is being archived. (Revised)
4. If you are posting copyrighted work...
5. Authors should refer to "Guidelines for posting on Usenet"...
(Revised)
6. When you reply to a message, do not change the subject line...
7. Comp.groupware is read by over 47,000 people.

------------ End of Contents (and revision information) ----------


0. Groupware is software and hardware for shared interactive
environments.

The term "environment" includes software and hardware that sets the
context for interaction. Hardware can include specially designed
furnishings and architectural spaces that are considered integral to
correct utilization of a given software application. A groupware
application may require a specific organizational environment to
function as expected. More powerful applications can adapt to, or
overcome limitations of, their environments.

The term "interactive" is used to indicate that time constraints are
managed by the system. Many groupware applications appear to support
real-time interaction. Others merely enforce deadlines that can span
weeks. In either case, the technical limitations on the pace of
interaction are made (to appear) negligible in terms of the objectives
of the application. Systems that exclude reference to real time are not
groupware applications.

The term "shared" indicates that two or more participants interact with
one another in such a manner that each person influences and is
influenced by each other person. No upper limit in the number of
participants is indicated, because mediated groups, as opposed to
natural ones, can maintain joint awareness with very large numbers of
persons. (Joint awareness is one way that "group" is defined.) An
objective of some groupware applications is to increase the number of
persons that can interact "as a group".

Some definitions of groupware include the notion of a common goal. While
all systems require some agreement among participants (at minimum that
they should be jointly used), interactions can be predominately
conflictual. Management of conflict is often a crucial feature of a
groupware system. Vote collecting systems are an example.

Definitions:

Group - Two or more persons who are interacting
with one another in such a manner that each person
influences and is influenced by each other person
(Shaw, M. E. _Group dynamics: The psychology of
small group behaviour_. 1976, p. 11).

Ware - 1 a) manufactured articles, products of art
or craft.... b) an article of merchandise.... 3) an
intangible item (as a service) that is a marketable
commodity. (_Webster's New Collegiate Dictionary_,
1976, p. 1319).


1. Set your distribution to "world". Comp.groupware is delivered to all
continents. Do not limit your chances for feedback by restricting
distribution. Restricted distribution can cause confusion when people
read responses to articles they have not seen. If you notice an article
has a restricted distribution, inform the poster by mail.

If you are restricted from posting to "world" by your administrator,
request a change in your privileges, at least for this newsgroup. If
refused, determine what your rights are in terms of appeal, based upon
information available at your site. An alternative is to use the Net to
find information and persons to contact concerning your rights.
Try the newsgroups:

comp.org.eff.news
comp.org.eff.talk
misc.legal.computing
alt.society.civil-liberty
alt.comp.acad-freedom.news
alt.society.cu-digest

A frequently asked questions file can be retrieved by sending email to:
[e-mail],
include the line "send caf-faq netnews.writing".
Information about the Electronic Frontier Foundation (EFF) can be
requested from [e-mail]. You can also retrieve information about EFF
and its projects via anonymous FTP from ftp.eff.org.

As a final resort, send a summary of your case to:

Carl Kadie ([e-mail])
Electronic Frontier Foundation
155 Second Street
Cambridge, MA 02141, USA
Tel.: [phone]
Fax: [phone].

If you can send email off-site, you can post using a Usenet-news mail
server. Email to "[e-mail]" is posted with the
subject line of your letter becoming the subject line of the article.
(Note: "." in the newsgroup name is written as "-".) This allows you to
post to a newsgroup even if you have read-only access to Network News.


2. Sign your article. Each name should have one and only one user. If
the article is a joint product, indicate this at the beginning and end
of the article. Some news reading programs allow certain names to be to
be automatically selected. Help the reader by using the same name at all
times. This will improve the chances that people will read your
articles.

The signature should include complete name, address, and telephone
number (this allows quick verification in case forgery is suspected).
E-mail addresses ought to be included in the signature in case headers
get munged. Another nice feature is geographical coordinates, so the
time zone can be determined (useful in telephoning). The signature
should be limited to four lines as is suggested practice on Usenet.


3. Comp.groupware is being archived. Selected discussions will be
reprinted in the _Writings on Computer Science_ (_Datalogiske Skrifter_)
working paper series available from the Institute of Geography,
Socio-economic Analysis, and Computer Science, Roskilde University, Post
Box 260, DK-4000 Roskilde, Denmark (ISSN 0109-9779-xx). Material
appearing in the series can be published elsewhere.

Authors will not be contacted individually before publication, but the
draft will be posted to comp.groupware for comment and correction before
being sent to the printer. All articles will be reproduced exactly as
posted (headers may be included, and parts (e.g., data sets) may be
moved to appendices and other changes making the articles more suitable
for printing may be made).

[e-mail] (Terry Myerson) began archiving comp.groupware 92.10.6.
The archive is available by anonymous ftp from:
avs.ncsc.org ( 128.109.178.23 )

in the directory:
~ftp/newsgroups/comp.groupware

The archives are in mail folders named MONTH_YEAR.
For example, to peruse all of the postings in the month of
October, you could download the archive Oct_92, and execute

%       Mail -f Oct_92

Articles from comp.groupware are also available by anonymous FTP from:
gorm.ruc.dk

in the directory:
~groupware/art/comp/groupware/

Login as "anonymous" and give your user name as your password.
Those without FTP access should send e-mail to:
[e-mail]

with "send usenet/news.answers/finding-sources" in the body to find out
how to do FTP by e-mail.


4. If you are posting copyrighted work, indicate at the beginning of the
article whether permission has been obtained. If you do not want an
article reproduced, indicate this (e.g., Copyright - Net distribution
only).


5. Authors should refer to "Guidelines for posting on Usenet" in the
newsgroup "news.announce.newusers" to make sure they know to spell check
their articles, etc. "Answers to Frequently Asked Questions",
"Introduction to news.announce", "Hints on writing style for Usenet"
available in the same newsgroup also contain information for new users.

Do not post test messages to comp.groupware. There are special groups
for testing. And tests should be as limited in their distribution as
possible. This is basic information from "Guidelines for posting on
Usenet". Posting of test messages inappropriately is considered abusive
and will cause a loss of readership for your articles.

Always use your Subject line to state the *topic* of your article as
completely as possible (e.g., "Macintosh II voice-mail based real-time
meeting software ready.", rather than "Meeting software"). Summary lines
should indicate *what* your message says about the topic (e.g., "New
meeting coordination software available via anonymous FTP"). Statements
should always end with periods, questions with question marks
(typically), and high energy, high impact declarations with exclamation
points. These rules makes articles much easier for recipients to handle
appropriately.

If you ask a question, your subject line should include "question",
"query", "(Q)" or should end with a "?". Questions should clearly
explain your problem and surrounding issues. Otherwise, you will simply
waste the time of those who want to help you. Tell people the kind of
work you are doing or contemplating doing. This helps them provide the
information you need. Indicate what efforts, if any, you have made thus
far, and what information was found.

Subject, Summary, and Keyword headers are scanned by many news reading
programs, thus permitting readers to find your article easily. You will
have your articles read more often if you select these carefully.


6. When you reply to a message, do not change the subject line or
redirect follow-ups (unless you are changing the subject).  Such changes
make it harder for some news readers to follow the threads in a
discussion. Include a "Summary" line which indicates specifically what
your message says. This permits your article to be found even if it is a
follow-up to an article with poorly chosen subject and keyword
information.

Please, do not post responses to articles you feel are inappropriate or
abusive. (If you can not resist, consider alt.flame as an alternative
newsgroup for your article [it has greater readership than
comp.groupware]). If the author is not saying anything worth reading,
enter the name in your "kill" file, and then no more of your time will
be wasted by that person. If you feel that the author is saying
something worth reading, but in an inappropriate way, respond by mail.
Tell the author what you think is incorrect about the article. If
possible, suggest how to accomplish the objective in an appropriate way
(e. g., post to another newsgroup). If you have responded to a person by
mail a few times without the desired effect, and you feel that the group
as a whole could benefit by a solution to the problem, only then should
you post an article.  The nature of your article should be a suggestion,
if possible, of how such problems can be avoided in the future.


7. Comp.groupware is read by over 47,000 people. Consider the cost to
readers of any post. If even an obviously inappropriate article is
distributed, one that just takes readers a few seconds to scan, and then
skip or kill, the total time used is still large. With 36,000 readers, a
post that takes an average of 1 second for each reader to deal with (i.
e., examining the subject line) means a total of ten hours used (36,000
seconds / 3,600 seconds/hour = 10 hours). If the article uses up an
average of four seconds, then the total time expenditure is 40 hours,
the equivalent of a work week. This is probably the minimum time
expenditure on any article that is even selected for scanning. So, if
you spend a week preparing an article and then post it to
comp.groupware, there will be a balance between your time investment and
that used by readers, even if they only scan your article and make no
response. The lack of a separate feedback channel is an unfortunate
deficiency in the Network News system as it is currently structured.

This analysis should not discourage anyone from posting a simple
question. Some of the most interesting and valuable exchanges in
comp.groupware have resulted from such questions. However, authors must
not make such requests unnecessarily. On the other hand, a carefully
prepared article or a report of an extensive project may not receive any
comment at all. This could mean that the article is clear and error
free. It could also mean it was not of sufficient interest to anyone to
be read in detail. What can be assumed is that it was seriously
considered. This is a result of the currently low traffic level in
comp.groupware and high quality of articles posted.

If your email reply to an author fails, try again using information in
the signature lines. An X.500 directory information server can be
consulted to find a person's email address. Read the informational
article, "How to find people's email addresses" (in the newsgroup
"news.answers"), so you know to contact the postmaster at the site of
the person you are trying to reach, and so on. Do not post a reply until
you have tried to reach the author by telephone, facsimile, or paper
mail. If these fail, ask yourself if getting the reply through is worth
ten hours of readers' time. If so, post the message. Do not post a
message asking a person to send you an email address, unless your letter
must be kept private (If this is true, consider using encryption). If it
is not of general interest, use only the person's name as the subject
(e.g., "To: Foo Bar"). If other readers might find it interesting, also
give full subject information.

Similarly, do not broadcast requests for information you can obtain from
a known source. Requests such as, "What are the contents of book Foo
published by Bar" are not appropriate. This information can normally be
obtained by a short telephone call and a few minutes of work by someone
being paid to provide that service. Let's not deprive someone of a job
and at the same time get comp.groupware readers fired because they are
wasting all their time reading unnecessary articles :-).

Post long articles as a single unit if they are less than 30,000
characters. Otherwise, post separate sections as follow-ups to the
first, breaking at meaningful places. This permits the sections to be
treated as a single unit, thus minimizing expenditure of attention on
the article. The cost of transmitting articles is negligible, so long
posts that take one second to delete "cost" the same as short ones.

Disregarding these considerations or a lack of self discipline in
following them will result in defensive attention management. That is,
certain authors will not be read at all by many readers or valuable
discussions will take place by email instead of being posted. This would
have the unfortunate effect of fractionating the joint awareness that
permits the comp.groupware readership to function as a group. Thus, it
is recommended that authors who prefer entertainment to rigor in their
news reading, post to other newsgroups.

-------

This article compiled with assistance from numerous readers of
comp.groupware.

Corrections, comments, and suggestions to:

David S. Stodolsky                Messages: + 45 46 75 77 11 x 24 41
Department of Computer Science                 Tel: + 45 31 95 92 82
Bldg. 20.1, Roskilde University Center        Internet: [e-mail]
Post Box 260, DK-4000 Roskilde, Denmark        Fax: + 45 46 75 42 01
MZ≡
█Æ ╢≡!â≡^në≡≡wp╣n7≡≡ía& wò&Gu≡òo]≡â2ÜSkâ2V≡`âífâíÜír╝vÜí≡v≡é£íî£í≡«J≡Eú├£╖í≡≡≡mEí≡≡Eí≡Eí╝Eí=Eí╓≡?Eí
Eí^║
WV≡Fß
£U┬
F#≡≡≡íXref: bloom-picayune.mit.edu rec.radio.amateur.misc:29832 news.answers:4597
Newsgroups: rec.radio.amateur.misc,rec.radio.info,rec.answers,news.answers
Path: bloom-picayune.mit.edu!enterpoop.mit.edu!news.media.mit.edu!micro-heart-of-gold.mit.edu!news.bbn.com!noc.near.net!uunet!europa.asd.contel.com!howland.reston.ans.net!sol.ctr.columbia.edu!news.unomaha.edu!cwis!pschleck
From: [e-mail] (Paul W Schleck KD3FU)
Subject: Index to the rec.radio.amateur.* Supplemental Archives
Message-ID: <[e-mail]>
Followup-To: poster
Summary: This article provides an excellent "read me first" list
         of VERY helpful files for this newsgroup and amateur
         radio in general, available via anonymous FTP from
         ftp.cs.buffalo.edu.
Keywords: radio, ham, amateur, ftp
Sender: [e-mail] (UNO Network News Server)
Supersedes: <[e-mail]>
X-Posting-Frequency: posted on the 15th of each month
Reply-To: [e-mail],[e-mail] (Archive Coordinators)
Organization: ACM Student Chapter, University of Nebraska at Omaha
Date: Tue, 15 Dec 1992 12:02:34 GMT
Approved: [e-mail]
Expires: Fri, 29 Jan 1993 06:00:00 GMT
Lines: 159

Posted-By: auto-faq script
Archive-name: ham-archives-index

The following is a list of informational files for this newsgroup
available via anonymous FTP from ftp.cs.buffalo.edu (currently at IP
number 128.205.32.9).

Questions to [e-mail]

1750m.band        - misc info on the 1750m band
ampr_coordinators    - coordinators for packet IP addresses
antenna_refs        - references for articles about antenna designs
arrl-logo.ps        - ARRL logo in PostScript format
arrl_bib        - bibliographies from ARRL literature (ASCII format)
arrl_digital_minutes    - Minutes of the ARRL committee on digital comm.
arrl_fo_jobs        - descriptions of some ARRL Field Organization jobs
arrl_info_service    - announcement of the ARRLs trial information service
cal_pd_freq        - California police frequencies
callbook.tar.Z        - sources for the marvin callsign server v1.3
canadian.Z        - Canadian ham database in FCC format
carpet.loop.2        - Antenna for apartments and small spaces
clubcalls.Z        - database of US ham clubs
comb6.zip        - HF Propagation Predication program
docket_91-36        - information regarding the proposed scanner regs
dxcc-k2di        - ARRL DXCC country list
element_credit        - rules about VE credit for earliers exams
elmers_admin        - information about the elmers list (see below)
elmers_list        - list of elmers on the network
exam_ops        - info on exams and exam opportunities
faq_ham_1        - frequently asked questions about ham radio (pts 1)
faq_ham_2        - frequently asked questions about ham radio (pts 2)
faq_ham_3        - frequently asked questions about ham radio (pts 3)
faq_packet        - frequently asked questions about packet radio
faq_shortwave        - frequently asked questions about shortwave
fft.com            - EGA/VGA DOS command for spectral display (QST 1/92)
ffth.com        - Hercules DOS command for spectral display (QST 1/92)
field_day_92        - field day rules for 1992
florida_antenna        - Florida State antenna law info
guide2newsgroups    - description of USENET newsgroups dedicated to radio
ham_sat_sum        - summary of information needed to get on satellite
hams_on_usenet        - list of ham operators and e-mail addresses on the net
hamstacks        - information about the question pool stacks
handicap_waiver        - info on obtaining a handicapped test waiver
hf_rigs            - QST reviews of available HF rigs
ht_info            - general information about commercial hand helds
intro_to_swl        - info for aspiring short wave listeners
intro_to_scanners    - info for aspiring scanner listeners
lead_acid_batteries    - essay on lead-acid batteries
license_plates        - guide to ham calls on license plates
logos            - PostScript logos for various ham organizations
mail_order        - a database of electronic mail order shops
manufacturers        - names and addresses of ham gear manufacturers
new_packeteers        - helpful essays for new packeteers
newcomers        - tips and hints for those new to amateur radio
packet_clubs        - organizations you can get more packet info from
packet_gateways        - list of gateways from packet to Internet
packet_misc        - miscellaneous packet info
packet_software        - list of packet software versions
phone_bbs_list        - phone BBSs for ham related issues/software
pio_handbook        - ARRL Public Information Officer's Handbook
pr_docket_92-136    - text of FCC PR Docket 92-136
qsl_bureau1        - information about the ARRL QSL bureau
qsl_bureau2        - "what should I do if" list for the QSL bureau
qst_prodrev        - index of ARRL product reviews in QST
repeater_map_proj    - description of Electronic Repeater Mapping Project
rfi_tips        - good posting about RFI
sol_geo_data        - desciption of daily solar geophysical broadcasts
sol_terra_terms        - glossary of solar-terrestrial terms
sstv_wefax_info        - general help for SSTV and WEFAX users
usenet_purchases    - tips on buying and selling via USENET

For readers of this newsgroup both new and experienced, these files are
a de-facto "Required Reading List" to provide definitive answers and
pointers to other sources for questions that come up in this forum.

This is also your archive, so any additional articles, guides, or small
PostScript graphics that you feel would enhance this collection are most
welcome.  Submit to Devon via his E-mail address above.

Additional archives out there that have /pub/ham-radio directories are
encouraged to "mirror" these files to provide redundant storage for these
documents.  Some of these sites (which may or may not mirror
ftp.cs.buffalo.edu) include:

ucsd.edu                        128.54.16.1     /hamradio
nic.funet.fi                    128.214.6.100   /pub/ham
csseq.cs.tamu.edu               128.194.2.20    /ham-radio
suntan.tandem.com               130.252.10.8    /hamradio
col.hp.com                      15.255.240.16   /packet
talos.cs.buffalo.edu            128.205.32.9    /pub/ham-radio
hamster.business.uwo.ca         129.100.22.100  /hamster/ham
                                                /hamster/tcpip
                                                /hamster/mods
                                                /hamster/view
vax.cs.pitt.edu                 130.49.2.1      /pub/arrl8
                                                /pub/ka9q
                                                /pub/ncpa
                                                /pub/tnc2
brolga.cc.uq.oz.au              130.102.128.5   /pub/ka9q
tomcat.gsfc.nasa.gov            128.183.10.100  /public
helios.tn.cornell.edu           128.84.241.2    /pub
wuarchive.wustl.edu             128.252.135.4   /mirrors/msdos/hamradio
                                                /mirrors/msdos/packet
                                                /mirrors/msdos/ka9q-tcpip
                                                /mirrors/cpm/hamradio
                                                /mirrors/cpm/packet
                                                /mirrors/misc/hamradio
                                                /mirrors/misc/packet
                                                /mirrors/misc/ka9q-tcpip
gatekeeper.dec.com              16.1.0.2        /pub/net/ka9q
sun.soe.clarkson.edu            128.153.12.3    /pub/ka9q
sics.se                         192.16.123.90   /archive/packet